I won't be able to review this for at least a couple of weeks.

My last push produced an error in a thread sanitizer check from code completely unrelated to mine , so I thought I'd try "fixing" the error by rebasing my branch to the latest master in hope that someone else already fixed the issue, and that resulted in the massive inclusion of all commits between the master my branch was originally based on and the latest master.

I tried to undo my rebase by force-pushing my last commit to the branch, but it still results in the code owners of all unrelated commits being tagged as reviewers for this PR by GitHub. Sorry about that.

This is why merge is better than rebase when updating PR.

This is why merge is better than rebase when updating PR.

Lesson learned. Thanks.

I've restored the previous reviewers list.

Thanks @blhsing for the PR, and @serhiy-storchaka for merging it 🌮🎉.. I'm working now to backport this PR to: 3.12.
🐍🍒⛏🤖

Thanks @blhsing for the PR, and @serhiy-storchaka for merging it 🌮🎉.. I'm working now to backport this PR to: 3.13.
🐍🍒⛏🤖

Sorry, @blhsing and @serhiy-storchaka, I could not cleanly backport this to 3.12 due to a conflict.
Please backport using cherry_picker on command line.

cherry_picker 126910edba812a01794f307b0cfa2a7f02bda190 3.12

Sorry, @blhsing and @serhiy-storchaka, I could not cleanly backport this to 3.13 due to a conflict.
Please backport using cherry_picker on command line.

cherry_picker 126910edba812a01794f307b0cfa2a7f02bda190 3.13